Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that a failed deployment is not created #172

Merged
merged 2 commits into from
Jun 13, 2024

Conversation

chadell
Copy link
Contributor

@chadell chadell commented Jun 13, 2024

Fix for #170

@chadell chadell marked this pull request as ready for review June 13, 2024 08:12
@chadell chadell requested review from abates and mzbroch as code owners June 13, 2024 08:12
@@ -268,6 +268,8 @@ def _run_in_transaction(self, **kwargs): # pylint: disable=too-many-branches, t
This version of `run` is wrapped in a transaction and will roll back database changes
on error. In general, this method should only be called by the `run` method.
"""
sid = transaction.savepoint()
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@abates , I think that is a better approach to rollback all the changes from a Design Job if it fails.
This means that neither a Deployment or a ChangeSet will be created if it fails or it's run in dry run mode.

@abates abates merged commit c73c675 into ltm-1.6 Jun 13, 2024
15 checks passed
@abates abates deleted the issue_170-design_job_failed branch June 13, 2024 11:06
@abates abates mentioned this pull request Jun 13, 2024
6 tasks
abates pushed a commit that referenced this pull request Jun 24, 2024
* tests: add a test to make sure that a failed deployment is not created

* fix: rollback the whole changes in a Design Job if something fails
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants